Onboarding Prerequisites
The following table summarizes the actions to perform for setting up the Operator Connect customer.
Onboarding Prerequisites
|
Step |
Action |
Management platform |
Tier |
Documentation Reference |
|||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Obtain Program Approval from Microsoft |
|
Service Provider Microsoft Entra ID Azure account |
AudioCodes Professional Services |
|
|||||||||
|
Setup AudioCodes Microsoft Entra ID for Operator Connect |
Instruct the service provider admin how to setup their Microsoft Entra ID for Operator Connect. |
Service Provider Microsoft Entra ID Azure account |
AudioCodes Professional Services |
|
|||||||||
|
Create App Registration |
Create an App Registration on Microsoft Entra Service Provider subscription. |
Service Provider Microsoft Entra ID Azure account |
AudioCodes Professional Services |
||||||||||
|
Deploy Application to AAD tenant |
Describe how to attach the Operator Connect application in Azure to the Microsoft Entra tenant and to assign Users and Groups. |
Service Provider Microsoft Entra ID Azure account |
AudioCodes Professional Services |
||||||||||
|
Fill JSON File |
|
JSON |
Service Provider admin |
|
|||||||||
|
Submit JSON file to Operator Connect Onboarding Team |
Open an ADO ticket and attach the JSON file to load into the system. |
ADO |
Professional Services or Service Provider admin |
||||||||||
|
Add sub-domains to Microsoft 365 to match the SBC certificate. |
Configure the subdomain FQDN that is configured in the certificate of the SBC trunk in Microsoft Azure. |
Microsoft Azure |
Professional Services |
||||||||||
|
Verify authentication to Live Platform portal. |
Verify that you can connect to the Live Platform portal with the relevant Microsoft Azure operators that are configured on the Enterprise application in your Microsoft Entra ID. |
Multitenant portal |
Professional Services or Service Provider admin |
||||||||||
|
Validate the SBC Domain |
Validate the domain FQDN that is configured in the certificate of the SBC trunk in the Microsoft 365 admin center. This FQDN must also be configured in the DNS server configuration (see below). |
Microsoft Admin Center |
Professional Services |
||||||||||
|
Define all Trunks on DNS Server (Configure DNS A-records for each managed SBC device). |
Configure service provider domain that is used by its’ customers for direct routing registered in Azure DNS, so that it can be configured by Live Platform. A record pointing to SBC FQDN should be created for each SBC site location name (Short Customer name). |
AudioCodes Azure Portal |
Professional Services |
||||||||||
|
Configure Teams Trunks (SBC devices) |
Configure all SBC devices |
Multitenant Portal |
Professional Services |
Configure Teams Trunk |
|||||||||
|
Test access to the Operator Connect portal |
The Operator Connect portal is a back end interface for managing Operator Connect functionality between Live Platform and Microsoft. It is used mainly for managing leads, configuring trunks and calling profiles and for number configuration. |
Operator Connect portal |
Professional Services |
Test Access to the Operator Portal |
|||||||||
|
Configure Calling Profiles |
The Calling Profiles should be configured including:
|
Operator Connect portal |
Professional Services |
Once configured, verify they have been synchronized to Live Platform Multitenant portal (seeManaging Calling Profiles). |
|||||||||
|
Provide Teams Test Tenant |
Provide onboarder with a maximum of 3 Teams test tenants to be used for pre-production testing. |
|
Professional Services |
|